v0.152.0

Compare Source

🛑 Breaking changes 🛑

• connector/span_metrics: Promote connector.spanmetrics.includeCollectorInstanceID feature gate to beta. (#​40400)
  Adds a collector.instance.id attribute to all metrics emitted by the spanmetrics connector.
• pkg/coreinternal: Promote internal.coreinternal.goldendataset.DontEmitV0NetworkConventions and internal.coreinternal.goldendataset.EmitV1NetworkConventions feature gates to Beta (#​46680)
  Both feature gates should be promoted together as per RFC.
• pkg/coreinternal: Promote internal.coreinternal.goldendataset.DontEmitV0RPCConventions and internal.coreinternal.goldendataset.EmitV1RPCConventions feature gates to Beta (#​46680)
• processor/tail_sampling: Stabilize disableinvertdecisions feature gate. (#​47650)
• receiver/kafka_metrics: Promote the receiver.kafkametricsreceiver.UseFranzGo feature gate to stable (#​41480)
  The franz-go client is now the only implementation; the gate is now permanently enabled and will be removed in v0.154.0.
  The Sarama-based implementation has been removed.

🚩 Deprecations 🚩

• connector/otlp_json: Rename component type from otlpjson to otlp_json to follow snake_case naming convention. The old name is kept as a deprecated alias. (#​48019)
• connector/round_robin: Rename component type from roundrobin to round_robin to follow snake_case naming convention. The old name is kept as a deprecated alias. (#​48021)
• connector/slow_sql: Rename component type from slowsql to slow_sql to follow snake_case naming convention. The old name is kept as a deprecated alias. (#​48020)
• exporter/bmc_helix: Rename exporter type from bmchelix to bmc_helix (#​45339)
• extension/kafkatopics_observer: Deprecate the kafkatopicsobserver extension in favor of using kafkareceiver directly (#​48186)
• processor/metrics_transform: Rename processor type from metricstransform to metrics_transform (#​45339)
• receiver/aws_lambda: Rename awslambda receiver to use lower_snake_case name aws_lambda. (#​45339)
• receiver/cloud_foundry: Rename receiver type from cloudfoundry to cloud_foundry (#​45339)
• receiver/google_cloud_spanner: Rename receiver type from googlecloudspanner to google_cloud_spanner (#​45339)
• receiver/kafka_metrics: Rename kafkametrics receiver to kafka_metrics with deprecated alias kafkametrics (#​45339)
• receiver/kubelet_stats: Rename receiver type from kubeletstats to kubelet_stats (#​45339)
• receiver/tcp_check: Rename tcpcheck receiver to tcp_check with deprecated alias tcpcheck (#​45339)

🚀 New components 🚀

• extension/mcp: Add new MCP server extension component. (#​48072)
• processor/cardinality_guardian: Add cardinalityguardianprocessor. (#​47368)
• processor/genainormalizer: Add a processor that normalizes GenAI telemetry attributes from OpenInference and OpenLLMetry to the official OTel GenAI Semantic Conventions. (#​46069)

💡 Enhancements 💡

• all: Support building with AIX (#​47010)

• cmd/opampsupervisor: Add support for declarative telemetry.resource configuration while preserving legacy inline resource attributes (#​45116)
  cmd/opampsupervisor now accepts typed telemetry resource configuration,
  including declarative resource attributes and detectors, and validates
  unsupported mixed or deprecated forms.
  Example:
  telemetry:
  resource:
  attributes:
  - name: service.name
  value: opamp-supervisor

• exporter/datadog: Add Kubernetes host alias provider to datadog exporter. (#​47199)
  In Kubernetes environments, the Datadog exporter now automatically adds nodeName-clusterName as a
  host alias in the host metadata payload. Both the node name and cluster name must be discoverable for the alias to
  be added; the cluster name is resolved from cloud provider metadata (Azure, EC2, or GCP).

• exporter/elasticsearch: Add ability to set filter_path in Elasticsearch exporter via the bulk_response_filter_path option. (#​47204)

• exporter/file: Allow usage of append mode with zstd compression (#​44382)

• exporter/kafka: Allow record_headers to accept multiple headers with the same key. (#​48092)

• exporter/loadbalancing: Add stable attribute routing key encoding for traces and metrics in the loadbalancing exporter (#​46094, #​46095)
  Routing keys now encode attributes as name=value| segments, including explicit markers for missing attributes.
  Non-string attribute values are deterministically stringified and used consistently across traces and metrics.

• exporter/opensearch: specify an ingest pipeline to be used before writing documents (#​47227)
  The pipeline option allows to specify an existing ingest pipeline that should process incoming documents.
  If the ingest pipeline does not exist, ingestion will fail.

• extension/aws_logs_encoding: Populate ECS fields from VPC Flow Logs as log record attributes (#​38861)
  Previously, VPC flow log fields prefixed with ecs- were skipped with a warning.
  They are now mapped to aws.ecs.* attributes on the emitted log record.

• extension/bearertokenauth: Update token file parsing to ignore everything after the first whitespace, allowing for inline comments. (#​46100)

• extension/cgroup_runtime: Expose refresh_interval for GOMEMLIMIT to support dynamic memory limits. (#​46768)

• extension/docker_observer: Add include_all_containers option to emit a port-less endpoint for every running container, including those with no exposed ports. (#​48252)
  When enabled, the observer emits a container endpoint with no port
  information for every running container, alongside any per-port endpoints.
  This allows receiver_creator rules of type == "container" to attach
  receivers to every container regardless of whether it exposes ports.
  Defaults to false for backwards compatibility.

• extension/kafkatopics_observer: Switch to the franz-go client. (#​48169)
  This is another step towards consolidating on franz-go for all Kafka components.
  We have already switched the receiver and exporter, and they are working well.

• extension/mcp: Register available tools with MCP server. (#​48103)

• extension/pebble_tail_storage: Add initial implementation of the Pebble tail storage extension. (#​47916)

• pkg/faro: Emit k6_testRunId in the log body when meta.k6.testRunId is present in the Faro payload. (#​47935)
  Surfaces the k6 test run identifier that the Faro Web SDK already
  forwards from window.k6.testRunId, alongside the existing
  k6_isK6Browser key. The reverse (logs -> Faro) translator extracts
  it back into Meta.K6.TestRunID for round-trip parity.

• pkg/pdatatest: Introduce pmetrictest.ValidateMetrics to strictly validate duplicate datapoint identities. (#​48106)

• processor/attributes: Added support for default values in the attributes processor. (#​45352)
  This enhancement allows users to specify default values for attributes in the attributes processor.
  If the primary value source (e.g., environment variable, attribute, or context value) is not available,
  the default value will be used. This ensures that the pipeline doesn't fail due to missing configuration.

• processor/drain: Add drain processor to k8s distribution. (#​47235)

• processor/k8s_attributes: Improve deployment name extraction heuristic when deployment_name_from_replicaset is enabled (#​44831)
  When deployment_name_from_replicaset is true and the ReplicaSet informer is not used for deployment names only,
  the processor derives k8s.deployment.name using the pod-template-hash label and ReplicaSet naming rules.
  When a ReplicaSet informer is running (for example for k8s.deployment.uid), API-backed metadata takes precedence,
  independent of the deployment_name_from_replicaset setting.

• processor/k8s_attributes: Add watch_sync_period config option to configure informer cache resync period. (#​48111)
  The watch_sync_period config option defaults to 5m to match the previously hardcoded behavior.

• processor/k8s_attributes: Use PartialObjectMetadata for non-Pod informers (#​47389)
  Switch Namespace, Node, Deployment, StatefulSet, DaemonSet, and Job informers
  from full typed objects to PartialObjectMetadata via the metadata client.
  These resources only need labels, annotations, UID, name, and owner references—all available
  in object metadata—so fetching full spec/status is unnecessary overhead.

  Pods continue using full objects since they require spec/status
  fields (pod IP, node name, containers, host network).

• processor/resource: Added support for default values in the resource processor. (#​45352)
  This enhancement allows users to specify default values for attributes in the resource processor.
  If the primary value source (e.g., environment variable, attribute, or context value) is not available,
  the default value will be used. This ensures that the pipeline doesn't fail due to missing configuration.

• processor/schema: Add internal metrics for schema translation skip rate and cache hit/miss (#​47638)
  Five new metrics are emitted via the collector's internal telemetry:

  • otelcol_processor_schema_logs.skipped
  • otelcol_processor_schema_metrics.skipped
  • otelcol_processor_schema_traces.skipped
  • otelcol_processor_schema_cache.hits
  • otelcol_processor_schema_cache.misses

  The skip counters increment when a scope has no schema URL at either the scope
  or resource level, making silent pass-throughs observable. The cache counters
  track effectiveness of the in-memory schema cache in CacheableProvider.

• receiver/awsfirehose: awsfirehose receiver now attempts gzip decompression for Firehose records before decoding. (#​46463)

• receiver/azure_event_hub: Expose the Prefetch option for Azure Event Hub receiver (#​48038)

• receiver/couchdb: Enables dynamic metric reaggregation in the CouchDB receiver. This does not break existing configuration files. (#​46351)

• receiver/googlecloudmonitoring: Allow overriding default endpoint for googlecloudmonitoringreceiver (#​47984)
  Adds an endpoint property which overrides the default monitoring.googleapis.com:443 endpoint.
  This is needed when targeting non-standard universe domains (e.g. S3NS: https://docs.cloud.google.com/sovereign-controls-by-partners/docs/data-boundaries/france-data-boundary-s3ns)

• receiver/k8s_cluster: Enable the re-aggregation feature for the k8s_cluster receiver (#​46361)

• receiver/k8s_events: Simplified RBAC example in README to only include required events resource permission. (#​48192)
  A namespace-scoped Role can also be used when the receiver is configured with specific namespaces.

• receiver/kafka: Add support for custom consumer-group partition-assignment strategies via extensions that implement kgo.GroupBalancer. Set group_rebalance_strategy to the component ID of a registered extension to use a custom balancer. (#​48096)
  The four built-in strategies (range, roundrobin, sticky, cooperative-sticky) continue to work unchanged.
  Any other value for group_rebalance_strategy is now resolved as an extension component ID at runtime.

• receiver/kafka: Cache OTel metric attribute sets in broker hook callbacks to reduce per-read allocations (#​47395)
  OnBrokerRead previously rebuilt attribute sets on every call. The computed
  MeasurementOption is now cached per (nodeID, outcome) key and evicted on
  broker disconnect. Growth is bounded by 2 × number-of-brokers.

• receiver/kubelet_stats: Add optional system container metrics (cpu.time, cpu.usage, memory.working_set) to kubeletstats receiver. (#​3531)

• receiver/memcached: Enables dynamic metric reaggregation in the Memcached receiver. This does not break existing configuration files. (#​46364)

• receiver/mysql: Added 'mysql.query_plan' to query sample records collected (#​47413)

• receiver/mysql: Fix the query hash generation for MySQL queries when the query is not explainable. (#​48059)

• receiver/nsxt: Enables dynamic metric reaggregation in the NSX-T receiver. This does not break existing configuration files. (#​46369)

• receiver/prometheus_remote_write: Add debug logging when dropping histograms with invalid schema values (#​48027)

• receiver/sqlserver: Adds idle blocking sessions to db.server.query_sample by appending sleeping blocker rows (with sqlserver.command=IDLE_BLOCKER) when blocker session IDs are missing from active requests. (#​47120)
  Idle blocker enrichment is best-effort: a targeted secondary idle-session query runs only for missing blocker session IDs, and failures are logged as warnings without failing the scrape.

🧰 Bug fixes 🧰

• connector/service_graph: Fix PR 47971 not add WithDeprecatedTypeAlias option in NewFactory() (#​47971)

• exporter/elasticsearch: Return permanent errors for non-retryable HTTP responses to prevent unnecessary upstream retries. (#​47870)

• exporter/kafka: Fix collector hanging indefinitely on shutdown when the Kafka broker is unreachable (#​48140)
  Re-enables the exporterhelper timeout sender (previously disabled with a zero timeout) so that each send attempt is bounded by the configured timeout (default 5s). The per-attempt context is now passed through to ProduceSync, allowing in-flight sends to unblock when the broker is unreachable. FranzSyncProducer.Close also cancels the kgo client context before calling client.Close, ensuring shutdown completes promptly.

• extension/health_check: Fix deadlock when the collector run context is cancelled while the healthcheck extension is present. (#​47591)

• extension/healthcheckv2: Fix deadlock when the collector run context is cancelled while the healthcheck extension is present. (#​47591)

• extension/opamp: Decorrelate service.instance.id and OpAMP instance_uid (#​46495)
  Previously:

  • the service.instance.id reported in the AgentDescription was based on the OpAMP instance UID
  • the instance UID was typically set based on the service.instance.id from the Collector resource attributes
  • it could be overriden using the instance_uid configuration of the OpAMP extension

  This meant that the reported service.instance.id did not always match the Collector resource attributes,
  which is a problem for correlation, and that server implementations got used to the typical case of
  service.instance.id and instance_uid matching, despite there being no guarantee of this.

  Now:

  • the reported value of service.instance.id always matches the Collector resource attributes
  • the instance UID is either taken from the instance_uid configuration or generated randomly.

  This means that the two values can never be expected to match, unless both configurations are explicitly set to the same value.
  That is what the OpAMP supervisor does, which means its behavior is unaffected.

• extension/sumologic: Fix variable shadowing and formatting issues in tests. (#​46602)

• processor/k8s_attributes: Fix a data race when reading the kube-system namespace from the client cache to populate the k8s.cluster.uid attribute. (#​47910)
  The ClusterUID rule in extractPodAttributes accessed the shared Namespaces
  map without acquiring the client's read lock, which could race with writes from
  the namespace informer. The access now goes through the locked GetNamespace
  helper.

• processor/k8s_attributes: Fix container.image.tags config check (#​47113)

• processor/tail_sampling: Fix sampling inconsistencies when using span-ingest sampling strategy (#​47476)

  1. Drop policies were not working if the initial batch did not contain a span matching the drop policy.
  2. If max_spans or upper_threshold_ms were respectively set on span_count or latency policies they may not have been respected.

• receiver/awsxray: support for fileystem sql urls (#​47361)
  Support for parsing sql urls without a hostname.

• receiver/datadog: Fix infinite memory growth in metrics translator by pruning stale streams that have not received data within the configured series_idle_timeout. (#​45523)
  Previously, high cardinality tags would cause the receiver to retain state indefinitely, leading to OOM.

• receiver/faro: Emit standard receiver telemetry (#​48070)
  The receiver constructed an ObsReport but never invoked it, so standard
  metrics like otelcol_receiver_accepted_log_records,
  otelcol_receiver_refused_log_records, otelcol_receiver_accepted_spans,
  and otelcol_receiver_refused_spans were not emitted. The consume calls
  are now wrapped with StartLogsOp/EndLogsOp and
  StartTracesOp/EndTracesOp so the standard receiver metrics are
  reported.

• receiver/host_metrics: Fix duplicate rootPath prefix in filesystem mountpoint translation (#​47083)
  When gopsutil falls back to reading /proc/self/mountinfo, the reported
  mountpoints already contain the rootPath prefix. This caused
  translateMountpoint to add it a second time, resulting in incorrect paths
  like /hostfs/hostfs/data.

• receiver/mysql: Strip leading SQL comments before EXPLAIN check so queries prefixed with block or line comments are correctly identified as explainable. (#​46587)

v0.151.0

Compare Source

🛑 Breaking changes 🛑

• all: Removed DNS lookup processor skeleton. (#​47874)

• connector/datadog: Remove stable feature gate connector.datadogconnector.NativeIngest (#​47580)

• exporter/datadog: Remove stable feature gates exporter.datadogexporter.UseLogsAgentExporter and exporter.datadogexporter.metricexportnativeclient (#​47583)

• exporter/signalfx: Default api_url and ingest_url values derived from realm now use *.observability.splunkcloud.com instead of *.signalfx.com. (#​47670)
  Explicit api_url and ingest_url settings are unchanged. Update network allowlists if they targeted only *.signalfx.com.

• exporter/splunk_hec: Remove deprecated batcher config field. Use sending_queue::batch instead. (#​47737)

• extension/jaegerremotesampling: Remove replaceThriftWithProto feature gate. (#​47553)

• pkg/translator/prometheus: Removes pkg.translator.prometheus.NormalizeName feature gate which has been stable for some time. (#​47597)

• pkg/zipkin: Promote "pkg.translator.zipkin.DontEmitV0NetworkConventions" and "pkg.translator.zipkin.EmitV1NetworkConventions" feature gates to Beta. (#​46682)
  This changes the default behavior to emit the new semantic convention attributes instead of the old deprecated ones.
  The Zipkin translator will now use network.local.address (replacing net.host.ip), network.peer.address (replacing net.peer.ip),
  and service.peer.name (replacing peer.service) by default when emitting spans.

• processor/k8s_attributes: Disable otelcol.k8s.pod.association metric until pod_identifier attribute is properly calculated (#​47669)

• receiver/jaeger: Stabilize DisableRemoteSampling feature gate which has been in beta for over 2 years. (#​47599)

• receiver/prometheus: Remove receiver.prometheusreceiver.EnableNativeHistograms, receiver.prometheusreceiver.RemoveStartTimeAdjustment and receiver.prometheusreceiver.UseCreatedMetric feature gates. (#​40606)

• receiver/prometheus: Removes the feature gate receiver.prometheusreceiver.RemoveLegacyResourceAttributes which has been stable for some time. (#​47598)

🚩 Deprecations 🚩

• connector/service_graph: Rename component type from servicegraph to service_graph to follow snake_case naming convention. The old name is kept as a deprecated alias. (#​47971)
• connector/span_metrics: Rename component type from spanmetrics to span_metrics to follow snake_case naming convention. The old name is kept as a deprecated alias. (#​47963)
• exporter/honeycomb_marker: Rename exporter type from honeycombmarker to honeycomb_marker (#​45339)
• exporter/prometheusremotewrite: add_metric_suffixes is deprecated. Use translation_strategy: UnderscoreEscapingWithoutSuffixes if you are setting this to false. (#​33661)
• extension/aws_logs_encoding: Deprecates transparent gzip decompression in aws_logs_encoding and clarifies that callers must decompress payloads before invoking the streaming decoder. (#​46463)
• processor/log_dedup: Rename processor type from logdedup to log_dedup (#​45339)
• receiver/file_stats: Rename filestats receiver to file_stats with deprecated alias filestats (#​45339)
• receiver/fluent_forward: Rename receiver type from fluentforward to fluent_forward (#​45339)
• receiver/host_metrics: Rename hostmetrics receiver to host_metrics and add deprecated alias hostmetrics (#​45449)
• receiver/k8s_objects: Rename k8sobjects receiver to k8s_objects and add deprecated alias k8sobjects. (#​47440)
• receiver/ssh_check: Rename sshcheck receiver to ssh_check with deprecated alias sshcheck (#​45339)

🚀 New components 🚀

• extension/pebble_tail_storage: First PR for new Pebble tail storage extension (#​47916)

• processor/drain: Add drain processor that applies the Drain log clustering algorithm to annotate log records with a derived template string. (#​47235)
  The processor sets log.record.template (e.g. "user <*> logged in from <*>") on each log record.
  Downstream processors such as the filter processor can act on this attribute to, for example, drop
  entire classes of noisy logs by template string.

  Key features:

  • Configurable Drain parse tree parameters (depth, similarity threshold, max clusters with LRU eviction)
  • Optional seeding via known template strings or example log lines for stable templates across restarts
  • passthrough warmup mode (default) and buffer warmup mode that holds records until the tree has stabilized
  • Internal telemetry metrics: active cluster count gauge, annotated and unannotated record counters

• receiver/azure_functions: Initial implementation of the Azure Functions receiver to ingest logs from Azure Functions triggered by Event Hub. (#​43507)

💡 Enhancements 💡

• cmd/telemetrygen: Add new --timeout flag to set timeout for telemetrygen calls (#​47203)

• exporter/awss3: Add support for retry_on_failure (#​47592)

• exporter/azure_blob: Add sending_queue and timeout support (#​47654)
  The azureblobexporter now supports sending_queue (with persistent storage, batching, and consumer configuration) and timeout configuration, matching the awss3exporter pattern.

• exporter/clickhouse: Update the default logs table schema with an improved ORDER BY, materialized k8s/deployment attribute columns, and automatic ClickHouse 26.2+ full text search index selection. (#​47720)
  The logs table DDL now uses ORDER BY (toStartOfFiveMinutes(Timestamp), ServiceName, Timestamp) and includes a set of
  materialized __otel_materialized_* columns for common k8s/deployment resource attributes.
  When connecting to ClickHouse 26.2+, the exporter creates TYPE text() indexes for full text search on attributes and body;
  on older versions it falls back to bloom_filter / tokenbf_v1 indexes. Existing tables are not modified
  (CREATE TABLE IF NOT EXISTS), and the INSERT path remains compatible with both the old and new schemas.

• exporter/datadog: Include service.instance.id in OTLP resource attribute to Datadog metric tag mapping so it is sent as a metric tag by default. (#​47936)
  service.instance.id is required to enable OTel traffic metrics on Datadog Fleet Automation.
  This change adds it to coreMapping so it is emitted as a Datadog metric tag when converting OTLP resource attributes.

• exporter/elasticsearch: Refactor profiles attribute handling (#​47801)
  The Profiles signal changed the handling of attributes and moved resource attributes from Sample
  to ResourceProfiles. Refactor attribute handling in elasticsearch exporter to reflect this change.

• exporter/prometheusremotewrite: Add support for translation_strategy, which supports UnderscoreEscapingWithSuffixes, UnderscoreEscapingWithoutSuffixes, NoUTF8EscapingWithSuffixes, and NoTranslation. (#​33661)

• exporter/prometheusremotewrite: Add support for exemplar labels when using PRW 2.0 (#​33661)

• exporter/signalfx: Add support for PersistentVolume and PersistentVolumeClaim entity property updates. (#​47829)
  Handle k8s.persistentvolume and k8s.persistentvolumeclaim entities in both the
  metadata update and entity events paths. Label prefix stripping is skipped for
  these entities to preserve full property key names.

• exporter/signalfx: APM correlation now recognizes deployment.environment.name in addition to the deprecated deployment.environment attribute (#​47862)

• extension/aws_logs_encoding: Migrate CloudTrail log semconv RPC attributes from v1.38.0 to v1.40.0 via feature gates (#​47549)

• extension/aws_logs_encoding: Added auto-detection support for AWS Transit Gateway flow logs (#​46229)
  The VPC flow log unmarshaler now automatically detects and handles Transit Gateway (TGW) flow logs from S3.
  Detection is based on the presence of the "resource-type" field in log file headers.
  TGW-specific fields (tgw-src-vpc-id, tgw-dst-vpc-id, etc.) are now supported and mapped to appropriate attributes.
  No configuration changes required - auto-detection works with default vpcflow format settings.

• extension/azure_encoding: Add encoding.format scope attribute for metrics based on Azure resource provider (#​47537)

• extension/azure_encoding: Migrate semantic conventions to v1.40.0 (#​47543)

• extension/health_check: Enable keep-alives for the health check extension's HTTP and gRPC servers. (#​45837)

• pkg/coreinternal: Migrate semantic conventions to v1.40.0 (#​47548)

• pkg/faro: Translate new Faro payload fields Meta.Device, Meta.OS, App.InstallationID, and Exception.Fatal. (#​47708)

• pkg/ottl: Enhanced ParseSimplifiedXML by limiting the maximum XML nesting depth. (#​47851)

• pkg/ottl: Enhanced ConvertTextToElementsXML function by limiting the maximum XML nesting depth. (#​47873)

• pkg/ottl: Enhanced XML parsing by limiting the maximum XML nesting depth. (#​47766)

• pkg/ottl: Added debug-level logging when functions truncate or discard attributes (#​9730)
  Added logging to the truncate_all and limit functions for each record that had attributes truncated or discarded, as per the OpenTelemetry specification on attribute limits

• pkg/stanza: Timestamp operator - Add support for multiple timezone parsing (#​47594)

• pkg/zipkin: Migrate semantic conventions to v1.40.0 (#​47545)

• processor/drain: Promote Drain Processor from development to alpha stability and add to contrib distribution. (#​47235)

• processor/k8s_attributes: Allow k8sattributes processors to be shared between pipelines (#​36234)
  When the processor.k8sattributes.ShareProcessorBetweenPipelines feature flag is enabled, k8sattributes processors
  using the same configuration are shared between pipelines. This reduces the local cache size and the number of
  connections to the K8s API Server.

• processor/schema: Make CacheableProvider cooldown and retry limit configurable via cache_cooldown and cache_retry_limit. (#​47761)

• processor/spanpruning: Add cumulative histogram bucket support for latency distribution on aggregated summary spans (#​47277)

• processor/tail_sampling: Add distributed tracing instrumentation to tailsamplingprocessor to provide visibility into trace processing behavior and policy evaluation (#​43931)
  Adds trace spans for key operations:

  • tailsampling.ConsumeTraces: Tracks incoming traces/spans count
  • tailsampling.samplingPolicyOnTick: Records batch processing metrics and policy evaluation results

• processor/transform: Added extract_percentile_metric function to Transform processor for extracting percentiles as gauge metrics from histograms. (#​44316)

• receiver/awslambda: Add multi-format S3 log routing via the new encodings field in the S3 receiver configuration. (#​46458)
  The new encodings list field enables a single Lambda deployment to route S3 objects to
  different decoders based on their key prefix.

• receiver/awss3: add a flag to the s3 receiver to skip objects previously tagged as ingested. (#​47396)

• receiver/chrony: Enables dynamic metric reaggregation in the Chrony receiver. This does not break existing configuration files. (#​46350)

• receiver/chrony: Add file_mount_path config option for cross-namespace Unix datagram socket communication (#​46833)
  When the collector and chronyd run in separate containers with different network
  namespaces, Go's default abstract socket autobind fails because abstract sockets
  are namespace-scoped. The new file_mount_path option uses a directory on a shared
  volume to bind a random client socket, allowing chronyd to reply across namespaces.

• receiver/datadog: Migrate semantic conventions to v1.40.0 (#​47551)

• receiver/github: Promote traces to alpha stability (#​47894)

• receiver/github: Add job.check_run_id deterministic spans via the receiver.githubreceiver.UseCheckRunID feature gate (#​44856, #​45157)
  Feature gate receiver.githubreceiver.UseCheckRunID derives job, step, and
  queue span IDs from the GitHub check_run_id instead of the workflow job
  name. This allows in-action telemetry tools to reproduce matching span IDs by
  leveraging ${{ job.check_run_id }} and name exclusively instead of calling
  the GitHub REST API. Trace ID and root span ID are unchanged. Webhook payloads
  missing workflow_job.id are rejected while the gate is enabled; set the gate
  to disabled to accept them under the legacy scheme.

• receiver/googlecloudpubsub: Add debug log of the pubsub message when an encoding error occurs. (#​46662)
  When the configured encoder fails to decode a Pub/Sub message, a debug-level
  log is now emitted containing the message ID, attributes, and the underlying
  error. This log is emitted regardless of the ignore_encoding_error setting,
  making it easier to diagnose which messages are causing decoding failures.

• receiver/host_metrics: Add AIX to the process scraper's supported-OS allowlist. The AIX-specific scraper implementation is added separately. (#​47095)

• receiver/icmpcheckreceiver: Enables dynamic metric reaggregation in the ICMP Check receiver. This does not break existing configuration files. (#​46359)

• receiver/journald: Log the full journalctl command which facilitates debugging. (#​45619)

• receiver/k8s_cluster: Add PersistentVolume and PersistentVolumeClaim metrics, entity events, and metadata support. (#​47453)
  New metrics (all disabled by default): k8s.persistentvolume.status.phase,
  k8s.persistentvolume.storage.capacity, k8s.persistentvolumeclaim.status.phase,
  k8s.persistentvolumeclaim.storage.request, k8s.persistentvolumeclaim.storage.capacity.
  New entity types: k8s.persistentvolume, k8s.persistentvolumeclaim.

• receiver/k8s_events: Add resource version persistence to the k8s_events receiver to prevent duplicate events on collector restart. (#​47575)
  A new storage configuration option accepts a storage extension ID (e.g. file_storage).
  When configured, the receiver persists the latest resourceVersion after each watch event and
  resumes from it on restart, preventing duplicate events. The persisted resourceVersion is
  scoped per namespace, matching the behavior added to the k8sobjects receiver in #​46543.

• receiver/k8s_events: Expose reporting controller and reporting instance as part of kubernetes events (#​45289)
  This change adds a reporting controller and reporting instance to the kubernetes events receiver.
  This allows for better monitoring and reporting of events collected by the receiver.

• receiver/k8s_objects: When storage is configured, watch-mode objects automatically resume from the last seen resourceVersion across restarts, preventing event duplication. (#​46543)

• receiver/mongodb_atlas: Enables dynamic metric reaggregation in the MongoDB Atlas receiver. This does not break existing configuration files. (#​46365)

• receiver/mysql: Add MySQL <8 and MariaDB compatibility for query sample and top-query collection. The receiver now detects the server product and version at connect time and gates behavior accordingly. Changes include: (1) top-query collection uses a fallback template on MySQL <8 and MariaDB that omits query_sample_text (absent on those versions); (2) client.port and network.peer.port are now populated on MySQL 8.0.22+ via a lock-free join on performance_schema.processlist, and remain 0 on older MySQL and all MariaDB versions where this table is unavailable; (3) mysql.events_waits_current.timer_wait now uses a three-tier fallback — exact TIMER_WAIT for completed waits, a PS timer approximation for in-progress waits on MySQL 5.7+/8.0+, and thread.processlist_time (integer-second precision) as a universal fallback for MariaDB and older MySQL.
  (#​47302)
  Supported products and versions: MySQL 5.7.3+, 8.0+; MariaDB 10.5.2+, 11.x.
  See COMPATIBILITY.md in the receiver directory for a full version × feature matrix.

• receiver/mysql: Add mysql.events_statements_current.timer_wait attribute to db.server.query_sample events, exposing the elapsed execution time of the sampled statement in seconds. (#​47529)
  On MariaDB and for in-flight MySQL statements where TIMER_WAIT is unavailable, PROCESSLIST_TIME is used as a fallback.

• receiver/nginx: Enable the re-aggregation feature for the nginx receiver (#​46368)

• receiver/osquery: Promote the osquery receiver to alpha (#​47498)

• receiver/prometheus_remote_write: Translate prometheus metric unit names per opentelemetry spec. (#​46984)

• receiver/prometheus_remote_write: Add support for translating Prometheus Info and StateSet typed metrics to OTLP Non-Monotonic Sums. (#​47727)

• receiver/prometheus_remote_write: Handle all otel_scope_* prefixed labels per the Prometheus/OTLP compatibility spec. (#​47726)
  otel_scope_schema_url is now set as the instrumentation scope schema URL, and other otel_scope_<attr> labels become scope attributes (with the otel_scope_ prefix stripped), instead of being incorrectly added as metric data point attributes.

• receiver/receiver_creator: Makes the default file_log config configurable on the receiver creator discovery feature. (#​40769)

• receiver/redfish: Enables dynamic metric reaggregation in the Redfish receiver. This does not break existing configuration files. (#​46375)

• receiver/sqlquery: Add ignore_null_values config option to suppress NULL value warning logs (#​43985)

• receiver/sqlserver: Enriches db.server.query_sample log records in the SQL Server receiver with wait-derived fields by adding sqlserver.blocking.start_time, sqlserver.wait.resource.type, sqlserver.wait.resource.id, and sqlserver.lock.type. (#​47119)
  sqlserver.blocking.start_time is emitted only when sqlserver.blocking_session_id is positive; sqlserver.wait.resource.type and sqlserver.wait.resource.id are parsed from wait_resource; and sqlserver.lock.type maps lock waits to shared/exclusive.

• receiver/ssh_check: Enables dynamic metric reaggregation in the SSH Check receiver. This does not break existing configuration files. (#​46380)

• receiver/statsd: Add ignore_host option to disable source IP-based aggregation (#​45387)

• receiver/tcpcheck: Enables dynamic metric reaggregation in the TCP Check receiver. This does not break existing configuration files. (#​46382)

• receiver/tls_check: Enables dynamic metric reaggregation in the TLS Check receiver. This does not break existing configuration files. (#​46383)

🧰 Bug fixes 🧰

• exporter/alibabacloud_logservice: Bump aliyun-log-go-sdk to v0.1.100, fixing SA1019 lint warning from deprecated producer.InitProducer (#​44363)
  Migrates to producer.NewProducer which returns an error, allowing initialization failures to propagate correctly.

• exporter/clickhouse: Quote cluster_name in ON CLUSTER clause to support names with special characters (e.g. dashes), preventing schema creation failures. (#​46946)

• exporter/datadog: Fix the dual shipping issue for orchestrator explorer in the datadog exporter. (#​47877)

• exporter/prometheus: Drop reserved instrumentation scope attributes from Prometheus exporter labels to avoid conflicts with scope metadata labels. (#​47924)

• exporter/prometheusremotewrite: Scope attributes "name", "version", and "schema_url" are dropped to prevent conflicts with the scope's name, version, and schema url fields. (#​47683)

• exporter/prometheusremotewrite: Fix bug where non-monotonic sums are mapped to Prometheus counters instead of gauges. (#​33661)

• exporter/prometheusremotewrite: Respect the zero threshold of exponential histograms when set for PRW v2 (#​33661)

• exporter/prometheusremotewrite: Skip attributes with empty string values when converting OTLP metrics to Prometheus labels. (#​47326)
  Attributes and resource attributes with empty string values are now excluded
  from Prometheus label conversion, preventing empty labels from being created.

• exporter/signalfx: Fix incorrect host_physical_cpus and host_cpu_cores values reported on Linux (#​47550)

• exporter/splunk_hec: Fix HEC routing partitioning broken when the exporterhelper batcher is enabled (#​47695)

• extension/azure_auth: Fix server-side authentication bypass by validating bearer tokens as OIDC JWTs with a server-pinned issuer and audience. (#​47823)
  Versions v0.124.0 through v0.150.0 accepted any bearer token that matched a token minted from the collector's own identity for a scope chosen by the client Host header, allowing authentication bypass and scope confusion.
  The receiver auth path now verifies the JWT signature against the issuer's JWKS and checks iss, aud, exp, and nbf. The audience is pinned from configuration and is never derived from request headers.
  Breaking change: using azure_auth under a receiver auth: block now requires the new server.issuer_url and server.audience settings. Exporter-only usage is unaffected.

• extension/azure_encoding: Fix parsing of all App Service and Function App log categories when properties field is a stringified JSON string instead of an object. ([#​47539](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/is

✂ Note

PR body was truncated to here.